Skip to content

ci(mergify): upgrade configuration to current format#1022

Open
mergify[bot] wants to merge 1 commit into
mainfrom
mergify/configuration-deprecated-update
Open

ci(mergify): upgrade configuration to current format#1022
mergify[bot] wants to merge 1 commit into
mainfrom
mergify/configuration-deprecated-update

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Apr 2, 2026 •
edited
Loading

Hey there! 👋

We've noticed that your Mergify configuration is using some deprecated fields.

No worries—we've got your back! This automated PR updates your config to align with the newest standards, ensuring everything keeps running smoothly.

Do not procrastinate! You must upgrade your configuration before 2026-07-31, otherwise your configuration will stop working.

What's Changed?

  • queue_rules → queue_branch_merge_method: Use merge_method: fast-forward instead of queue_branch_merge_method: fast-forward. See docs: https://docs.mergify.com/merge-queue/merge-strategies#fast-forward. (deadline: 2026-07-31)
  • The default value of merge_protections_settings.reporting_method is changing from check-runs to deployments. Your configuration has been updated to explicitly set check-runs to preserve current behavior. (deadline: 2026-07-31)

Why This Matters

Keeping your configuration up-to-date means you'll benefit from the latest features and improvements Mergify has to offer. Plus, it helps prevent any unexpected hiccups down the road.

Got Questions? We've Got Answers! 🙌

Is this update safe to merge?

Absolutely! We've made sure the changes are compatible with your current setup. Your workflows should continue to work just as before—if not better!

Do I need to do anything special after merging?

Nope! Just merge this PR, and you're all set. If you have any custom configurations, it's a good idea to give them a quick look to ensure everything's in order.

What if I run into issues or have concerns?

We're here to help! Feel free to reach out to our support team anytime.

Thanks for being awesome and keeping your configuration up-to-date! If you have any thoughts or need a hand, don't hesitate to let us know.

Happy merging! 🎉

@mergify mergify Bot requested a review from MH0386 as a code owner April 2, 2026 08:45
@semanticdiff-com
Copy link
Copy Markdown

semanticdiff-com Bot commented Apr 2, 2026 •
edited
Loading

Review changes with  SemanticDiff

Changed Files
File Status
  .github/mergify.yml  35% smaller

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented Apr 2, 2026 •
edited
Loading

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Mergify merge queue configuration to use the new merge_method field instead of the deprecated queue_branch_merge_method, keeping behavior equivalent while aligning with the current Mergify format.

Flow diagram for PR merging with fast-forward merge_method

flowchart TD
  PR_open["Pull request opened"]
  Conditions_match["Mergify pull_request_rules match"]
  Add_to_queue["Add PR to merge queue default"]
  Rebase_update["Update PR using update_method merge"]
  Queue_branch_ff["Apply merge_method fast-forward on queue branch"]
  Main_branch_update["Fast-forward main branch"]
  PR_merged["PR marked as merged"]

  PR_open --> Conditions_match
  Conditions_match --> Add_to_queue
  Add_to_queue --> Rebase_update
  Rebase_update --> Queue_branch_ff
  Queue_branch_ff --> Main_branch_update
  Main_branch_update --> PR_merged
Loading

File-Level Changes

Change Details Files
Migrate Mergify queue configuration from deprecated queue_branch_merge_method to merge_method while preserving existing fast-forward behavior and queue settings.
  • Remove deprecated queue_branch_merge_method: fast-forward from the queue rule configuration.
  • Keep allow_queue_branch_edit: true and update_method: merge unchanged to preserve queue behavior.
  • Ensure the queue rule still has a name: default entry for identification.
  • Add merge_method: fast-forward to explicitly configure fast-forward merging using the new field.
 .github/mergify.yml
Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

sourcery-ai[bot]
sourcery-ai Bot reviewed Apr 2, 2026
View reviewed changes
Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@deepsource-io
Copy link
Copy Markdown

deepsource-io Bot commented Apr 2, 2026 •
edited
Loading

DeepSource Code Review

We reviewed changes in ce416b0...bf2bd33 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Security  

Reliability  

Complexity  

Hygiene  

Code Review Summary

Analyzer Status Updated (UTC) Details
Docker Apr 3, 2026 10:14a.m. Review ↗
Secrets Apr 3, 2026 10:14a.m. Review ↗
Python Apr 3, 2026 10:14a.m. Review ↗

@mergify
Copy link
Copy Markdown
Contributor Author

mergify Bot commented Apr 2, 2026

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 📃 Configuration Change Requirements

Wonderful, this rule succeeded.

Mergify configuration change

  • check-success = Configuration changed

@mergify mergify Bot force-pushed the mergify/configuration-deprecated-update branch from bafc404 to 9e8c7bc Compare April 2, 2026 08:57
@mergify mergify Bot force-pushed the mergify/configuration-deprecated-update branch from 5fd0070 to ce416b0 Compare April 3, 2026 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sourcery-ai sourcery-ai[bot] sourcery-ai[bot] left review comments

@MH0386 MH0386 Awaiting requested review from MH0386 MH0386 is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants